Date: Tue, 31 May 94 04:30:32 PDT From: Ham-Space Mailing List and Newsgroup Errors-To: Ham-Space-Errors@UCSD.Edu Reply-To: Ham-Space@UCSD.Edu Precedence: Bulk Subject: Ham-Space Digest V94 #141 To: Ham-Space Ham-Space Digest Tue, 31 May 94 Volume 94 : Issue 141 Today's Topics: ARLK021 Keplerian data LUSAT-1 (LO-19): Actual status Welcome to rec.radio.info! Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Space Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-space". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sat, 28 May 1994 16:34:34 EDT From: psinntp!arrl.org!usenet@uunet.uu.net Subject: ARLK021 Keplerian data To: ham-space@ucsd.edu SB KEP @ ARL $ARLK021 ARLK021 Keplerian data ZCZC SK88 QST de W1AW Keplerian Bulletin 21 ARLK021 ------------------------------ Date: 28 May 94 14:16:57 GMT From: news-mail-gateway@ucsd.edu Subject: LUSAT-1 (LO-19): Actual status To: ham-space@ucsd.edu Official LUSAT-1 Status Report The satellite LUSAT-1 seems healthy. The control station is actually performing some tests to the satellite. The satellite is sending telemetry on 437.125 MHz and it's digipeater still turned on. Overseas stations: If you capture any LUSAT-1 telemetry and send it in raw-mode to the satellite control station, you'll receive a certificate for your collaboration. These telemetry reports can be sent either via packet radio to LU8DYF@LU8DYF.BA.ARG.SOAM and LU8DYF@ANY-ACTIVE-SATELLITE, or via Internet to: lu8dyf@asarin.org.ar If you intend to use the satellite, please remember that the BBS is NOT LOADED and it will NOT be operational for the next 3 weeks (approx.). The LUSAT-1 recovery team want to thanks all the stations that sent LUSAT-1 telemetry data in RAW format. The overseas stations that are going to receive the Special Award are: 1) Mr. Norimasa Okamoto (JN2LHU) from Gamagori city, Japan. 73's de Eduardo Sweet, LU7AKC (LUSAT-1 recovery team) packet: lu7akc@lu7akc.#col.cf.arg.soam e-mail: lu7akc@asarin.org.ar ------------------------------ Date: Mon, 30 May 1994 21:00:05 MDT From: tribune.usask.ca!quartz.ucs.ualberta.ca!alberta!ve6mgs!rec-radio-info@decwrl.dec.com Subject: Welcome to rec.radio.info! To: ham-space@ucsd.edu Archive-name: radio/rec-radio-info/welcome Last-modified: $Date: 1994/01/02 22:00 $ Version: $Revision: 1.06 $ *** Welcome to rec.radio.info! *** Welcome to rec.radio.info, a group that aims to provide a noise-free source of information and news for the entire rec.radio hierarchy. Two introductory articles about rec.radio.info are posted to the group and to news.answers every two weeks. You are now reading the first article, which explains what rec.radio.info is, and answers some Frequently Asked Questions. The second article is titled "Submission Guidelines", and you only need to read it if you want to submit an article to rec.radio.info. You can skip to the next section of this article by searching for the next " -- " string. The sections available are: - What is the purpose of rec.radio.info? - Why are messages almost always cross posted to rec.radio.info? - What is a 'follow-up', and what does 'moderated' mean? - OK, so now I know what 'moderated' means. Tell me more. - What type of material is considered inappropriate? - I do not have access to news, how can I get the information posted to rec.radio.info? - Will the material appearing in rec.radio.info be archived somewhere? - I have a regular posting with timely information, is there a way to speed up it's delivery, or automate for more convenience? -- What is the purpose of rec.radio.info? The purpose or charter of rec.radio.info is to provide the Usenet community with a resource for information, news, and facts about any and all things radio. All the other rec.radio groups are intended for discussions and general chit chat about radio. Rec.radio.info will contain informational, factual articles only. Follow-ups are redirected to an appropriate other group, and further discussion (if any) will not take place in rec.radio.info. In order to ensure that rec.radio.info contains only appropriate articles, it was decided to create the group as a moderated newsgroup. -- Why are messages almost always cross posted to rec.radio.info? It provides a "tag" for each article to be assembled into a filtered presentation in rec.radio.info (even with cross-posting, only one message, with a unique Message-ID, is propogated across the net). This tag also facilitates a pre-existing method of dropping or cancelling the articles locally within the discussion groups if you don't want to see them. This accommodates individuals who want to separate the bulletins from the discussions, discussions from the bulletins, as well as those who are adamant about not reading another newsgroup and wanted to see everything all in one basket. With the total size of Usenet (in number of newsgroups and total traffic) doubling every year or so, this is no insignificant contribution to reducing information noise and chaos. Making the discussion groups a catch-all, and making extra newsgroups filters on that catch-all, is also the most realistic way to implement such a scheme (It's not intuitively obvious what the charter, contents, and general appropriate topics for each and every newsgroup are. Seeing FAQ's and charter/intro postings in the home newsgroup is beneficial for new readers). By cross-posting one only is adding a few tens of bytes to each bulletin (to specify the extra group on the Newsgroups line), but are adding the capability for very powerful filtering features available on most news servers, listservers and readers. Your local news guru could probably explain these features in more detail. In rn, for example, according to Leanne Phillips in her rn kill-file FAQ, add a line of the form: /Newsgroups:.*[ ,]rec\.radio\.info/h:j either in ~/News/KILL (if you don't want to see rec.radio.info articles anywhere) or ~/News/rec/radio/amateur/misc/KILL (if you don't want to see them just in rec.radio.amateur.misc). The latter method means your kill file will only be consulted during rec.radio.amateur.misc (and hence runs more efficiently), and will probably work for most people. In nn, according to Bill Wohler in his nn FAQ, add a line of the form: rec.radio.info:!s/:^ in ~/.nn/kill (if you don't want to see rec.radio.info articles anywhere), or put the following lines: sequence rec.radio.info rec.radio. at the end of ~/.nn/init in order to see all the rec.radio.info bulletins first, then read the remaining rec.radio.* without the bulletins. -- What is a 'follow-up', and what does 'moderated' mean? If you are new to Usenet and are not familiar with the terminology, you might want to read the general introductory articles found in the newsgroup news.announce.newusers. Doing so will make your life on the net much easier, and will probably save you from making silly beginner's mistakes. If you think that at this moment you are reading an echo, a conference, or a bulletin board, I'd also strongly suggest a trip over to news.announce.newusers. For the rest of this article, I will assume you have a basic knowledge of Usenet terminology and mechanics. A moderated group means that any article that needs to be posted to the group has to be accepted by the moderator of the group. Since we need to ensure that followups to an article (discussion) do not show up in the rec.radio.info newsgroup, the `Followup-To:' header line contains a newsgroup that is appropriate for disussions about the specific article. -- OK, so now I know what 'moderated' means. Tell me more. Rec.radio.info is a moderated newsgroup, which means that all articles submitted to the group will have to be approved by the moderator first. The current moderator of the group is Mark Salyzyn. Submissions to rec.radio.info can be posted, or e-mailed to: rec-radio-info@ve6mgs.ampr.ab.ca Comments, criticisms, suggestions or questions about the group can be e-mailed to: rec-radio-request@ve6mgs.ampr.ab.ca But before you do so, please be sure to check out the "Submission Guidelines" article. The influence of the moderator should be minimal and of an administrative nature, consisting chiefly of weeding out obviously inappropriate articles, while making sure correct headers etc. are used for the appropriate ones. -- What type of material is considered inappropriate? There are three broad categories of articles which will be rejected by the moderator: 1) Requests for information: rec.radio.info is strictly a one-way street. I receive information in my mailbox; I then post it to rec.radio.info. Requests for specific information belong in the normal discussion newsgroups. If your request gets answered, you might consider passing the answer on to rec.radio.info, though. Especially if you can edit it into a informational, rather than a discussion, format. 2) Obvious discussion articles, or articles that appear unsubstantiated. 3) Commercial stuff: a relatively unbiased test of a radio product would be accepted, but any hint of for-profit might be reason for rejection. For three reasons: This is not the purpose of the list, for-profit is a controversial topic, and this list may be passed onto Amateur Packet Radio (where for-profit is prohibited except under certain provisos). rec.radio.swap (or possibly comp.newprod) may be more deserving of the posting in any matter. Similarly, copyrighted material generally cannot be used. If it's TRULY worthwhile to the net, I would recommend obtaining permission from the copyright holder. Please note the source, and if permission was given. I reserve the right to make the final decision concerning appropriateness in all situations. In most cases, a brief summary of, or pointer to, the copyrighted information may be all I can allow. -- I do not have access to news, how can I get the information posted to rec.radio.info? brian@UCSD.EDU (Brian Kantor) has kindly supplied a mail list server for rec.radio.info. Non of the articles will be digested, due to their size, so you will receive individual mailings for every article posted to the group. Mail sent to radio-info@ucsd.edu will be forwarded to the moderator and thus is an alias to rec-radio-info@ve6mgs.ampr.ab.ca To subscribe and unsubscribe via the listserver; the format for that is sub address radio-info unsub address radio-info where 'address' is your full mailing address. Send this request to listserv@ucsd.edu Note that the server will automatically delete any address that bounces mail. If you leave the address portion blank, it will try to deduce your address from the mail headers. This may not work if you are on bitnet, milnet or some other non-Unix host, so it is recommended to put your return address in any case. For example: sub mymailbox@myhost.mydomain.mil radio-info or sub MEMEME01@DMBHST.bitnet radio-info or something like that. -- Will the material appearing in rec.radio.info be archived somewhere? < Dated information here > Yes. Still firming up details at the moment but here is a preliminary list: - unbc.edu as maintained by Lyndon Nerenberg - nic.funet.fi maintained by Risto Kotalampi saved to /pub/dx/text/rec.radio.info currently stored as numbered files. Effectively this means that anything you post to rec.radio.info will be permanently stored, so your work will not be lost. -- I have a regular posting with timely information, is there a way to speed up it's delivery, or automate for more convenience? Yes, there is! It may take a bit of chatter with the moderator, but we are willing to take responsible people and provide them the means of posting the articles directly from their site. We will try everything we can as we fully realize that DX (distant signal) and astronomical data can be somewhat transitory. We are also willing to allow regular posters of information the same courtesy, even if the information is not as time critical. We refer to this as self-moderation, which is partly based on the model for news.answer. This requires co-operation and good will to be beneficial to the community in the rec.radio hierarchy. I suggest reading the posting guidelines for more information. I am open to suggestions. I thank the following individuals for their input into this article: rec.music.info moderator Leo Breebaart rec-music-info@cp.tn.tudelft.nl rec.radio.broadcasting moderator Bill Pfeiffer wdp@gagme.chi.il.us Paul W. Schleck, KD3FU pschleck@unomaha.edu Ian Kluft, KD6EUI ikluft@uts.amdahl.com -- Mark Salyzyn -- Moderator rec.radio.info Submissions to: rec-radio-info@ve6mgs.ampr.ab.ca Administrivia to: rec-radio-request@ve6mgs.ampr.ab.ca * Requests for information do *not* belong in rec.radio.info * ------------------------------ Date: (null) From: (null) SB KEP ARL ARLK021 ARLK021 Keplerian data Thanks to NASA, AMSAT and N3FKV for the following Keplerian data. Decode 2-line elsets with the following key: 1 AAAAAU 00 0 0 BBBBB.BBBBBBBB .CCCCCCCC 00000-0 00000-0 0 DDDZ 2 AAAAA EEE.EEEE FFF.FFFF GGGGGGG HHH.HHHH III.IIII JJ.JJJJJJJJKKKKKZ KEY: A-CATALOGNUM B-EPOCHTIME C-DECAY D-ELSETNUM E-INCLINATION F-RAAN G-ECCENTRICITY H-ARGPERIGEE I-MNANOM J-MNMOTION K-ORBITNUM Z-CHECKSUM STS-65 1 99965U 94999A 94189.76632148 0.00073311 21920-3 0 22 2 99965 28.4664 14.3253 0003598 331.2635 28.7780 15.90320458 27 AO-10 1 14129U 83058B 94142.44873866 -.00000055 10000-3 0 2859 2 14129 27.1282 326.3729 6021350 180.2426 179.1822 2.05879809 54280 RS-10/11 1 18129U 87054A 94143.06202902 0.00000033 19805-4 0 9045 2 18129 82.9244 347.4186 0013145 90.9237 269.3425 13.72337109346469 UO-11 1 14781U 84021B 94147.04880050 0.00000219 45013-4 0 6968 2 14781 97.7872 162.7641 0011793 344.0205 16.0623 14.69213466547207 RS-12/13 1 21089U 91007A 94144.13470258 0.00000037 23586-4 0 6959 2 21089 82.9224 29.2888 0029039 172.4887 187.6707 13.74040914165344 AO-13 1 19216U 88051B 94147.27035052 -.00000441 10000-4 0 9208 2 19216 57.8366 250.5249 7207923 342.4663 2.0218 2.09724553 14073 UO-14 1 20437U 90005B 94144.22276841 0.00000025 26693-4 0 9978 2 20437 98.5880 229.3217 0010181 263.8728 96.1295 14.29843487226168 AO-16 1 20439U 90005D 94144.20928715 0.00000020 24847-4 0 7963 2 20439 98.5965 230.5154 0010403 264.3951 95.6036 14.29897339226172 DO-17 1 20440U 90005E 94144.16596132 0.00000045 34314-4 0 7961 2 20440 98.5981 230.7887 0010560 263.4989 96.4992 14.30037037226186 WO-18 1 20441U 90005F 94144.21082933 0.00000033 29788-4 0 7985 2 20441 98.5971 230.8353 0011035 263.3967 96.5956 14.30011373226195 LO-19 1 20442U 90005G 94144.19061234 0.00000040 32455-4 0 7954 2 20442 98.5977 231.0663 0011451 263.1040 96.8842 14.30107216226202 FO-20 1 20480U 90013C 94144.43473962 -.00000035 -10249-4 0 6926 2 20480 99.0329 300.7480 0541340 33.2966 330.0992 12.83225622201086 AO-21 1 21087U 91006A 94146.99633645 0.00000094 82657-4 0 4745 2 21087 82.9417 158.3928 0036111 140.7337 219.6450 13.74540016166678 UO-22 1 21575U 91050B 94144.18192998 0.00000065 36633-4 0 4994 2 21575 98.4364 219.1638 0008301 8.5029 351.6298 14.36915556149634 KO-23 1 22077U 92052B 94144.52572252 -.00000037 10000-3 0 3941 2 22077 66.0839 329.5255 0013803 293.2557 66.7013 12.86286047 83740 KO-25 1 22830U 93061H 94144.19534348 0.00000045 35671-4 0 2989 2 22830 98.5540 217.7814 0010495 247.7152 112.2919 14.28053943 34275 IO-26 1 22826U 93061D 94144.24944208 0.00000023 27369-4 0 2936 2 22826 98.6505 220.3266 0008712 287.1330 72.8895 14.27727519 34278 AO-27 1 22825U 93061C 94144.19661163 0.00000028 29274-4 0 2937 2 22825 98.6515 220.2413 0008078 284.8036 75.2246 14.27623773 34266 PO-28 1 22829U 93061G 94144.20009399 0.00000042 34857-4 0 2861 2 22829 98.6480 220.3002 0009356 270.1364 89.8754 14.28025735 34279 Mir 1 16609U 86017A 94147.26457637 0.00004646 71844-4 0 6241 2 16609 51.6477 290.9923 0001594 334.7802 25.3132 15.56209705472788 Keplerian bulletins are transmitted twice weekly from W1AW. The next scheduled transmission of these data will be Tuesday, May 31, 1994, at 2230z on Baudot and AMTOR. NNNN /EX ------------------------------ End of Ham-Space Digest V94 #141 ******************************